-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Limit the use of a pointer to the lexical scope of the target #120342
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR addresses a pointer scope issue by moving the declaration of a stack-allocated string and PKCS12 export parameters struct outside of a conditional block to ensure the pointer remains valid throughout its usage scope.
- Moved stack allocation of algorithm string and struct initialization outside conditional block
- Replaced local variable reference with the outer-scoped variable reference
- Ensured pointer validity by expanding the lexical scope of the target data
|
Tagging subscribers to this area: @dotnet/area-system-security, @bartonjs, @vcsjones |
...ty.Cryptography/src/System/Security/Cryptography/X509Certificates/StorePal.Windows.Export.cs
Outdated
Show resolved
Hide resolved
…/Cryptography/X509Certificates/StorePal.Windows.Export.cs Co-authored-by: Jan Kotas <[email protected]>
|
/backport to release/10.0 |
|
Started backporting to release/10.0: https://github.com/dotnet/runtime/actions/runs/18234052838 |
No description provided.